Skip to content

Conversation

@zrhoffman
Copy link
Contributor

Fixes #266

Making TokenSerializationType public is useful to describe a CSS string that is already known to be valid in cases when the TokenSerializationTypes of the start and end of the CSS string is needed, but Tokens are not.

This helps with creating a custom_properties::VariableValue from the CSS string of a computed value for CSS Properties and Values, see Mozilla bug 1858305 1.

Making TokenSerializationType public is useful to describe a CSS string
that is already known to be valid in cases when the
TokenSerializationTypes of the start and end of the CSS string is
needed, but Tokens are not.

This helps with creating a custom_properties::VariableValue from the CSS
string of a computed value for CSS Properties and Values, see Mozilla
bug 1858305 [1].

[1]: https://bugzilla.mozilla.org/show_bug.cgi?id=1858305
@zrhoffman
Copy link
Contributor Author

r? @SimonSapin

@SimonSapin
Copy link
Member

Hi! I haven’t been involved in the maintenance of this crate for a few years now.

@zrhoffman
Copy link
Contributor Author

Hi! I haven’t been involved in the maintenance of this crate for a few years now.

My bad.

r? @emilio :)

@emilio
Copy link
Member

emilio commented Nov 14, 2023

FWIW for some reason your mention didn't get to my inbox. If I miss any other review request or what not let me know.

@emilio emilio added this pull request to the merge queue Nov 14, 2023
Merged via the queue into servo:master with commit aaa966d Nov 14, 2023
@zrhoffman zrhoffman deleted the token-serialization-type-enum branch November 14, 2023 14:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

No way to get TokenSerializationType directly

3 participants